Computer implemented methods and apparatus for composing and batch publishing feed items in a feed-based interaction context

ABSTRACT

Disclosed are methods, apparatus, systems, and computer-readable storage media for composing and batch publishing feed items in a user interface in a feed-based interaction context. In some implementations, a computing device provides a first prompt for display in a first user interface component, which is configured to display unpublished feed items. The computing device receives, at the first prompt, first feed item data for a first feed item. Responsive to a request to compose a second feed item, the computing device displays in the first user interface component a second prompt for second feed item data without publishing the first feed item. The computing device receives, at the second prompt, second feed item data for a second feed item of a first record, the first and second feed items being related to the first record.

PRIORITY DATA

This application claims priority to and commonly assigned U.S.Provisional Patent Application No. 61/675,442, filed on Jul. 25, 2012,entitled SYSTEM AND METHOD FOR PROVIDING AN IMPROVED SERVICE CONSOLE, byAl-Alami et al., which is hereby incorporated by reference in itsentirety and for all purposes.

COPYRIGHT NOTICE

A portion of the disclosure of this patent document contains materialwhich is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent file or records, but otherwise reserves all copyrightrights whatsoever.

TECHNICAL FIELD

The present disclosure relates generally to on-demand services providedover a data network such as the Internet, and more specifically to aconsole application for accessing and interacting with informationstored in the data network, for instance, in a database.

BACKGROUND

Organizations typically employ many different types of software andcomputing technologies to meet their computing needs. However,installing and maintaining software on an organization's own computersystems may involve one or more drawbacks. For example, when softwaremust be installed on computer systems within the organization, theinstallation process often requires significant time commitments, sinceorganization personnel may need to separately access each computer. Onceinstalled, the maintenance of such software typically requiressignificant additional resources. Each installation of the software mayneed to be separately monitored, upgraded, and/or maintained. Further,organization personnel may need to protect each installed piece ofsoftware against viruses and other malevolent code. Given thedifficulties in updating and maintaining software installed on manydifferent computer systems, it is common for software to becomeoutdated. Also, the organization will likely need to ensure that thevarious software programs installed on each computer system arecompatible. Compatibility problems are compounded by frequent upgrading,which may result in different versions of the same software being usedat different computer systems in the same organization.

Accordingly, organizations increasingly prefer to use on-demand servicesaccessible via the Internet rather than software installed on in-housecomputer systems. On-demand services, often termed “cloud computing”services, take advantage of increased network speeds and decreasednetwork latency to provide shared resources, software, and informationto computers and other devices upon request. Cloud computing typicallyinvolves over-the-Internet provision of dynamically scalable and oftenvirtualized resources. Technological details can be abstracted from theusers, who no longer have need for expertise in, or control over, thetechnology infrastructure “in the cloud” that supports them.

BRIEF DESCRIPTION OF THE DRAWINGS

The included drawings are for illustrative purposes and serve only toprovide examples of possible structures and process steps for thedisclosed inventive systems and methods for composing and batchpublishing feed items in a user interface in a feed-based interactioncontext. These drawings in no way limit any changes in form and detailthat may be made to embodiments by one skilled in the art withoutdeparting from the spirit and scope of the disclosure.

FIG. 1 shows a flowchart of an example of a method 100 for handling acall, performed in accordance with some implementations.

FIG. 2 shows a flowchart of an example of a method 200 for opening arecord, performed in accordance with some implementations.

FIG. 3A shows a system diagram of an example of architectural componentsof an on-demand service environment, in accordance with someimplementations.

FIG. 3B shows a system diagram further illustrating an example ofarchitectural components of an on-demand service environment, inaccordance with some implementations.

FIG. 4 shows a system diagram illustrating an example of thearchitecture of a multitenant database environment, in accordance withsome implementations.

FIG. 5 shows a system diagram further illustrating an example of thearchitecture of a multitenant database environment, in accordance withsome implementations.

FIGS. 6A and 6B show flowcharts of examples of methods illustratinginteractions of third party pages with the service cloud consoleenvironment, in accordance with one or more implementations.

FIGS. 7 and 8 show images of examples of user interfaces that may bepresented in a web browser at a client machine, in accordance with oneor more implementations.

FIG. 9 shows a flowchart of an example of a computer implemented method900 for composing and batch publishing feed items in a user interface ina feed-based interaction context, in accordance with someimplementations.

FIG. 10 shows a flowchart of an example of a computer implemented method1000 for composing and batch publishing feed items in a user interfacein a feed-based interaction context, in accordance with someimplementations.

FIG. 11 shows a flowchart of an example of a computer implemented method1100 for composing and batch publishing feed items in a user interfacein a feed-based interaction context, in accordance with someimplementations.

FIG. 12 shows an example of a graphical user interface (GUI) including apresentation of a user interface for publishing feed items, inaccordance with one or more implementations.

FIG. 13 shows an example of a graphical user interface including apresentation of a user interface for publishing feed items, inaccordance with one or more implementations.

FIG. 14 shows an example of a graphical user interface including apresentation of a user interface for publishing feed items, inaccordance with one or more implementations.

FIG. 15 shows an example of a graphical user interface including apresentation of a user interface for publishing feed items, inaccordance with one or more implementations.

DETAILED DESCRIPTION

Applications of systems and methods according to one or moreimplementations are described in this section. These examples are beingprovided solely to add context and aid in the understanding of thepresent disclosure. It will thus be apparent to one skilled in the artthat the techniques described herein may be practiced without some orall of these specific details. In other instances, well known processsteps have not been described in detail in order to avoid unnecessarilyobscuring the present disclosure. Other applications are possible, suchthat the following examples should not be taken as definitive orlimiting either in scope or setting.

In the following detailed description, references are made to theaccompanying drawings, which form a part of the description and in whichare shown, by way of illustration, specific implementations. Althoughthese implementations are described in sufficient detail to enable oneskilled in the art to practice the disclosure, it is understood thatthese examples are not limiting, such that other implementations may beused and changes may be made without departing from the spirit and scopeof the disclosure.

As used herein, the term “multi-tenant database system” refers to thosesystems in which various elements of hardware and software of thedatabase system may be shared by one or more customers. For example, agiven application server may simultaneously process requests for a greatnumber of customers, and a given database table may store rows for apotentially much greater number of customers.

Some implementations are directed to a user interface console providedat a client machine for interacting with object record informationstored in a multitenant database at a server in an on-demand serviceenvironment. Some implementations of the apparatuses, systems andmethods disclosed herein are adapted for use in other types of devices,systems or environments, as applicable, such that their use isapplicable in broader applications than the environments and contextsdescribed herein.

In the following figures, methods and apparatus applicable to variousservice cloud console configurations and their associated components aredescribed. In one or more implementations, the service cloud console maybe used to provide an on-demand, web-based system for accessing data andapplications. The service cloud console (alternately described as theconsole, the console application, the agent console, or the servicedesk) includes a user interface provided at a client machine forinteracting with object record information stored in storage facilitiessuch as databases at a server.

In one or more implementations, an agent of an organization who is usingan instance of a service cloud console application may receive a callfrom a client who has an account with the organization. Using theservice cloud console application, the agent may open, close, edit,and/or save object records associated with the client's account.

Certain components and services of the service cloud console may be usedto replace software for accessing data and managing customer recordstypically installed on separate computers in an organization. Forexample, the service cloud console may replace one or more CRM programs,call center programs, etc. By using the service cloud console, an agentfor an organization can access data associated with a client of theorganization.

Use of the service cloud console may be provided over data networks suchas the Internet to a plurality of different organizations. The datanetwork in which implementations of the service cloud console isimplemented may include other wide area networks (“WAN”) and local areanetworks (“LAN”), or portions thereof. In one or more implementations,different organizations may customize the service cloud console to suittheir own needs. For example, an organization may create more than oneconsole application, adjust the settings of a console application, applya name to a console application, etc.

In one or more implementations, the service cloud console may includeone or more graphical user interfaces tailored to maintain the contextof an account using a tab metaphor. Examples of selected portions ofsuch a graphical user interface according to one or more implementationsare shown FIGS. 7-8. The service cloud console may be componentized suchthat each tab can display and/or refer to all or selected portions ofgroups of information. For example, a tab or component in the servicecloud console may display all or selected portions of an individual rowof data in a database, data integrated from an external system, or anyother arrangement of data.

The system may be both easy for agents to use and easy foradministrators to manage. One or more implementations may facilitatespeed and simplicity, giving the agent the ability to navigate throughthe interface with a limited number of clicks, and without a great dealof training. One or more implementations may allow the agent to maintainthe context, or frame of reference, of a current call and prior calls inan easily navigable interface. One or more implementations may allow theintegration of external systems into a single, fluid agent interface.One or more implementations may improve access to a knowledge base,supplying the agent with the information he needs when he needs it.

In one or more implementations, certain components and services of theservice cloud console may reduce the number of clicks an agent needed tomake to perform a task. An agent's interaction with the consoleapplication is made as fast and as fluid as possible. Further, theconsole application maintains as much context as possible so the agentalways knows what he's doing and where he's been in the consoleapplication.

The following several paragraphs describe use cases for a fictionalindividual named Aaron. Aaron is a customer call center agent who usescall center software as part of his work. One or more implementationsdescribed herein may remedy one or more of the challenges faced byagents such as Aaron.

Aaron is handling a telephone call from a customer. Aaron also has agrowing queue of cases that have been assigned to him to handle. Aaronhas opened a case record for the customer he is helping in a primary tabof a service console page, such as a page displayed in a browser windowusing salesforce.com's Service Cloud Console™ service or other customerrelationship management (CRM) application or cloud-based CRM serviceprovided by salesforce.com or provided by other service providers. Inthis example, the service console page is displayed in a user interface(UI) on Aaron's computing device. Aaron would like to be able todiscover the issue that the customer is having, view the latest statusof what has been done for this customer on this issue, do some research,and perform a series of actions on the case at hand, and he would liketo do all of this with as few context switches as possible and with asfew clicks as possible in a logical, user-friendly way. The series ofactions that he may want to execute for a case may include writing anemail to the customer, writing an internal note for his reference or forother agents' reference, changing the status of the case from pending toresolved, or attaching a relevant article or file to the case. Aaronwould like to be able to perform any or all of these actions in aseamless, fluid process, so that he can quickly resolve the case, andmove on to the next case in his queue.

Using some of the disclosed implementations, Aaron may open a case,causing information about the case to populate the user interface thathe is viewing. In one area of the user interface, Aaron may view thelatest updates to the case to ascertain the status of the case. Otheragents may have worked on this case before, or done some research andattached some notes or files to the case. In this area of the userinterface, Aaron can view all of the recent updates to the case toquickly orient himself to determine what he needs to do next. In anotherarea of the user interface, Aaron can perform some research on theissue, finding articles or experts to assist with resolving the issue.In yet another area of the user interface, Aaron can open up any numberof prompts to write an email to the customer, to write an internal notefor the case, to change the status of the case, or to attach a file tothe case. Rather than having to open up one prompt, write an email, andpublish the email before opening up another prompt, Aaron is able toopen up as many prompts as he would like to compose, and then justpublish them all together with one click. For example, after discussingthe issue with the customer, Aaron may find a helpful article to give tothe customer to resolve his issue. Aaron may then compose an email tothe customer sending over the article, compose an internal noteidentifying the article as being helpful for resolving the issue, andchange the status of the case from pending to resolved. He compose eachof these updates, and then click one button to publish all of them. Insome cases, composing and publishing the updates may be all that Aaronneeds to do for that particular case, so clicking on the button topublish the updates may also cause the user interface to present thenext case in Aaron's queue.

The disclosed implementations provide Aaron a streamlined workflow fordealing with cases that involves fewer context switches and lower clickcounts, reduces repetitive tasks, such as publishing each update one ata time or selecting the next case in a queue, and provides a more fluidpublishing process, all saving Aaron valuable time.

While the disclosed implementations are often described with referenceto the example of a case, as in Aaron's scenario outlined above, thoseskilled in the art should appreciate that a case is one of many examplesof database records. The disclosed techniques are equally applicable toother various types of records, files, objects and other data constructsthat may be stored in a database or other suitable storage medium. Forexample, CRM objects such as leads, accounts, opportunities, contracts,and contacts may be substituted for case records in the examplesdisclosed herein.

User Interface Overview

FIGS. 7 and 8 show images of examples of user interfaces that may bepresented in a web browser at a client machine, in accordance with oneor more implementations. Different implementations may include varioususer interfaces. For example, the user interface shown in FIG. 8 has adifferent appearance than the user interface shown in FIG. 7. Thus, theclaims should not be construed as being limited to any particular userinterface(s).

In one or more implementations, the user interface of the service cloudconsole may include one or more of an overview area, a main view area704, a context view area 804, a sidebar area 808, a marquee area 708,and/or a highlights panel 724. The overview area may be a container inwhich components associated with the service cloud console, such ascomponents 704, 708, 712, 716, 720, 724, 728, 732, and 736, aredisplayed. The overview area may show components that span a large setof information (e.g., a list view).

The main view 704 may show the detail or edit page of a single object ora search results page. The context view 804 may show small but editableviews of objects that are related to the object in the main view. Thesidebar 808 may be positioned on the side of the screen and may includean ability to handle a wide range of components. The marquee 708 maydisplay a limited amount (e.g., one line) of informational text.

In some implementations, the main view 704 may display variousinformation associated with one or more object records that arecurrently open as a primary tab (alternately referred to as a workspace)in the console application. The main view 704 may display one or moresecondary tabs 712 that are each associated with the primary tab 716that has focus in the console application. When a different primary tab(e.g., primary tab 720) is selected, then the one or more secondary tabsassociated with the different primary tab may be displayed. The mainview 704 may include a UI tool such as a vertical and/or horizontalscroll bar 732 to navigate the displayed page.

In one or more implementations, the main view 704 may rarely beoverridden. For instance, search results and list views shown in themain view 704 may open new tabs rather than overriding the content ofthe main view 704 so that when the user navigates to an object, theresults of the search are not lost. Similarly, sub-operations likecreating tasks or sending emails may not override the content of themain view 704, but may use a technique such as an HTML <div> overlay tomaintain context. The main view 704 may support inline editing.

The highlights panel 724 may include an area in the workspace (e.g., atthe top) which gives the user information about the object controllingthat workspace. A “mutton” 728 may be displayed in the highlights panel724. The mutton 728 (alternately referred to as a multi-button) may be abutton that acts as a dropdown menu containing multiple functions. Themutton 728 may allow the agent to perform actions that would normally beperformed from buttons on related lists of the layout. The mutton 728may include various buttons, which can be shown, for example, if theentity happens to be in a related list on the layout of the workspaceentity, and if the button is shown in the layout for that related list.

One or more implementations may include a sidebar 808 that may bedisplayed on the side of the interface, as shown in FIG. 8. The sidebar808 may be a separate layout such that there is a specific consolesidebar component that is rendered in the console. The setup of thesidebar layout may be available in the console layout and may useconcepts similar to that used for home page layouts.

In one or more implementations, when displaying a record in the mainview area, the sidebar 808 may display one or more related lists, asshown in FIG. 8. The items displayed in the sidebar 808 may be navigatedby a UI tool such as a vertical scroll bar if the number of itemsexceeds the vertical space. In certain situations, such as when a recordis being edited, the sidebar 808 may be hidden.

The sidebar 808 may allow handling of various types of components, so itmay include an interface (e.g., a tab or accordion widget) to managethese components effectively (e.g., displaying them without sending thembelow the fold of the page). The sidebar 808 may include a pluggableinterface that has knowledge of the current context of the main page sothat third parties can create custom sidebar components.

The marquee 708 may be a short area (e.g., one character high) that maybe shown at the top and/or bottom of the screen. The marquee 708 mayshow fixed text and/or scrolling text. The direction of the scrollingtext may depend on the agent's preferred language (e.g., right to leftfor user languages like English that are left-to-right, and left toright for languages like Hebrew that are right-to-left). The API mayinclude a message object as a container for marquee messages. Messagerows may count towards storage (e.g., in the database).

One or more implementations may include a control 736 referred to as anavigation tab (alternately referred to herein as Silvertab) whichprovides agents access to various objects without leaving the console.The navigation tab 736 can be configured by the administrator(alternately referred to as an admin) to access various availableobjects. In some implementations, only objects designated as navigationtab items for the console will be listed in the navigation tab menu. Adefault item can be selected from the chosen navigation tab items. Oninitial view of the console, the end user may see the navigation tab 736in the top left region of the console with the default item name, color,and/or icon. In some implementations, the navigation tab 736 provides anapproximately 150 px width space for icon and text. An item label thatexceeds the available width (e.g., 150 px) may be truncated and appendedwith an ellipsis. In other implementations, the width space of thenavigation tab may be a different size.

In some implementations, the overview area may display general overviewinformation. The general overview information may be displayed using oneor more list views, dashboards, or custom components. One or moreimplementations may include an activity log 1212 for enteringinformation related to changes to the record, as shown in FIG. 8.

List views may include various capabilities, such as inline editing.When an object is clicked in the list view, it may raise an event thatopens one or more tabs that pertain to that object. One or more listviews may auto-update. For example, the list view may be configurable toauto-refresh at an interval (e.g., 5 minutes). One or more list viewsmay be multi-sortable (e.g., an agent may be able to select multiplecolumns by which to sort). One or more list views may include hovers, apreview icon that can be clicked to show a hover, or both. One or morelist views may include one or more visual indicators (e.g., indicatingwhether a new comment, email, or escalation has been added to a case).One or more list views may include a provision for mass actions.

One type of list view may be a universal inbox, which may contain a listof actionable items. This list may include (but is not limited to) newcases, leads, case comments, emails, tasks, and pending events. Oneadvantage of the universal inbox is that it can show many differenttypes of objects in one place and may allow users to prioritize them.

In one or more implementations, the overview area may be populable bydraggable dashboard components. The overview area may be able to containone or more of list views and/or dashboard components at the same time.A dashboard that is visible to a user may be available as a dashboardcomponent.

In some implementations, one or more of these views may be collapsible.Collapsible views allow views to be hidden if the agent does not desirethem there. The size of each of the views may be saved across sessionson a per-agent basis so that the agent does not have to re-layout hisconsole every time he navigates to it.

The URL format of the service cloud console may be regular and/orbookmarkable. For instance, if an agent is viewing a case detail page,the agent may be able to copy that URL from the browser and email it toa colleague. When the colleague clicks on that URL, the correspondingcase should appear in the main view of the colleague's console (even ifthe colleague's console is otherwise laid out differently).

FIG. 1 shows a flowchart of an example of a method 100 for handling acall, performed in accordance with some implementations. The callhandling method 100 may be performed to facilitate the handling of acall by an agent using the service cloud console. For example, the callhandling method 100 may be performed at a client machine incommunication with a server. The client machine may be running a webbrowser displaying a user interface representing an instance of theservice cloud console, such as the user interfaces shown in FIGS. 7 and8.

In some implementations, one or more of the operations shown in FIG. 1may be completed without refreshing the user interface or web pagedisplayed in the web browser at the client machine in which the userinterface is shown. Completing operations without refreshing the webpage may allow the agent to receive calls and to open, edit, save, andclose object records without significant interruptions.

At 104, a first record tab for accessing a first object record isprovided. In one or more implementations, the first object record tab isprovided in the user interface displayed in the web browser running atthe client machine. An example of such a tab is shown at 716 in FIG. 7.The first object record tab may display information associated with thefirst object record. The first object record may be, for example, adatabase object stored in a database on the server.

For example, the first object record may be a client account, or aportion of a client account, such as the account shown on tab 716 inFIG. 7. The first object record tab may then contain information relatedto the client account, such as one or more names, phone numbers, e-mailaddresses, or other contact information. Additionally, or alternately,the first object record tab may contain information such as billingdata, technical data, client preferences, or any other type ofinformation associated with the first object record in the database suchas the case information shown in the main view 704 in FIG. 7.

Although one or more implementations display object records as tabs asuser interface components, the user interface components for displayingobject records are not limited to being displayed in tabs. According tovarious implementations, different types of user interface componentsmay be used, such as window panes, windows, ribbons, 3D navigationenvironments, etc.

At 108, an incoming call is identified. The call may include anycommunication from an individual. In some instances, the call may be acommunication from an individual associated with an account accessiblevia the service cloud console. For example, the call may be acommunication from an individual associated with a customer of theorganization using the service cloud console application.

In one or more implementations, the incoming call may be a voice call.The voice call may be a telephone call transmitted over a telephonenetwork such as the public switched telephone network (PTSN), a voiceover IP (VoIP) call received over a computer network, a pre-recordedvoice call, or any other type of voice call. In some implementations,the incoming call may be another type of call, such as a text chatsession, an e-mail, a text message, or any other type of communication.

In some implementations, identifying the incoming call may includeidentifying a number from which the call originated (e.g., a PSTNnumber, a VoIP number, etc.). Alternately, identifying the incoming callmay include identifying a chat handle, a customer identification number,a URL, an e-mail address, or any other relevant identifier. However, insome instances the source of the incoming call may not be identified.

In one or more implementations, identifying the incoming call mayinclude identifying an account associated with the incoming call. Forexample, a database at the server may be queried using a numberassociated with the incoming call to identify an account associated withthe incoming call. In this case, the user interface may displayinformation associated with the incoming call, such as the name of aclient making the call, the name of an account associated with theclient, or other information.

In one or more implementations, the incoming call may be received by theagent. For example, the incoming call may be received within the userinterface displayed in the web browser by opening or activating a userinterface component associated with receiving a call.

As a different example, the incoming call may be received via adifferent program or web page at the client machine. For example, theclient machine may have dedicated software for receiving calls.Alternately, a separate user interface for receiving calls via a webbrowser may be displayed in a different tab or window of the webbrowser.

As yet another example, the incoming call may be received via a deviceother than the client machine, such as a telephone or headset. Thetelephone or headset may be communicatively coupled with one or both ofthe client machine or the server.

At 112, a second record tab for the incoming call is opened. When thesecond record tab is opened, the first record tab may be hidden fromview. One method for opening a record is discussed with reference toFIG. 2.

In one or more implementations, a tab ordering including a listing ofone or more previously accessed record tabs may be stored at the clientmachine. In this way, the focus of the user interface may beautomatically returned to the previous record tab (e.g., the firstrecord tab) when a subsequently accessed record tab (e.g., the secondrecord tab) is closed.

In one or more implementations, the second record tab may be openedautomatically. For example, when the incoming call is identified, aquery may be transmitted to a database at the server to identify anobject record associated with the incoming call. When the record isidentified, the second record tab may then be opened automaticallyopened. Opening the second record tab automatically may save time forthe agent because the agent need not manually look up the client'saccount. Instead, the client's account may already be open so that theagent has access to the account information when handling the call.

Alternately, the second record tab may be opened manually (e.g., by theagent). For example, the agent may identify a record to open afterreceiving the call and receiving information from the client. Manuallyopening the second record tab may be necessary if, for example, theclient is calling from an unidentified source or a source not yetassociated with the client's account. In this case, the agent mayreceive information from the client and then provide input to the userinterface causing the identified object record to open.

In some instances, the second record tab may be associated with a new orblank object record. For example, the client may not be associated withan existing account, as may be the case for a new client. As anotherexample, the client may be establishing a new record associated with anexisting account.

At 116, user input for handling the incoming call is received. The userinput may include any information for handling the incoming call, suchas modifying account information for the client's account, adding newaccount information, establishing a new account for the client, deletingexisting account information, updating or entering account preferences,etc.

In some instances, one or more additional procedures may be triggeredduring or after the receipt of the user input. For example, one or moreinstances of a contextual sidebar update method and/or an edited pagedetection method may be triggered. Examples of these methods arediscussed with reference to FIGS. 5 and 6.

At 120, a request is received to close the second record tab. Therequest to close the second record tab may be received by detecting aclick of a close button on a primary tab, such as the primary tab 116shown in FIG. 7. In some instances, the received request may be anexplicit request to close the second record tab. For example, thereceived request may be the detection of user input in the userinterface such as clicking a “close” button or symbol, the detection ofa keyboard command that corresponds with a request to close the tab, orany other technique for receiving an explicit request to close thesecond record tab.

In some instances, the received request may be an implicit request toclose the second record tab. For example, the termination of the callmay in some instances trigger a request to close the second record tab.

In one or more implementations, receiving a request to close the secondrecord tab may trigger one or more procedures associated with ensuringthat edited data is saved to the server, such as the edited page savemethod shown in FIG. 4.

At 124, the second record tab is closed. When the second record tab isclosed, the second record tab may be removed from the user interface.Further, the first record tab may be revealed to the agent. Revealingthe first record tab when the second record tab is closed may allow theagent to quickly resume interacting with the first record tab, thusreducing the interruption caused by receiving the call.

FIG. 2 shows a flowchart of an example of a method 200 for opening arecord, performed in accordance with some implementations. The recordopen method 200 may be performed when the service cloud console userinterface is displayed in a web browser at a client machine. The servicecloud console interface may be open in a browser tab of a web browser ormay be the only page open in the browser.

In one or more implementations, the service cloud console may displayone or more user interface components for displaying object recordinformation associated with object records stored in a database. Objectrecords may include any database objects accessible via the servicecloud console. In some implementations, these user interfaces may bearranged according to a tab metaphor, as is illustrated in the userinterfaces shown in FIGS. 7-8. One or more implementations may use oneor more different types of user interface components, such as windows,window panes, pages, wizard guides, list boxes, tree controls, etc. Forexample, one or more implementations may employ a “wizard-style”interface in which an agent is led through one or more tasks (e.g.,using arrows). However, records are described herein as being displayedwithin tabs.

In one or more implementations, the service cloud console may displayone or more primary tabs (alternately referred to as workspace tabs). Asis shown in FIGS. 7 and 8, primary tabs may be arranged in adrag-and-drop user interface. The graphical user interface 700 shown inFIG. 7 includes a navigation tab 736 and primary tabs 716 and 720. Thegraphical user interface 700 also includes a highlights panel 724, amutton 728, and an activity log 708. The record opened in the primarytab is displayed in the main view 704, and in FIG. 8, the graphical userinterface 800 also includes a sidebar 808.

In one or more implementations, an individual primary tab may be closedusing a close button. When an individual tab is closed, the last-viewedprimary tab or the navigation tab may be brought into focus.

The graphical user interface shown in FIG. 7 includes a subtab bar 712.In one or more implementations, items or records other than the primarytab object opened within a primary tab may be displayed as subtabs insubtab bar 712. As with primary tabs, subtabs may be rearranged via adrag-and-drop interface, as shown in FIG. 7. However, one or moresubtabs may be arranged in a fixed position. For example, the accountdetail page associated with the primary tab record may be fixed as thefirst subtab in the subtab bar 712, as shown in FIG. 7.

The operations shown in FIG. 2 illustrate a method for opening a recordtab according to one or more implementations. The service cloud consolemay be operable to open and/or close record tabs without refreshing theweb page in which the service cloud console user interface is displayed.Thus, an agent may open and/or close record tabs, which may includecommunications between the client machine and the server, withoutinterrupting the user of the service cloud console.

At 204, an action to open a new tab for a record is identified. In someinstances, the identified action may include an action taken by a userwith the intention of opening a new record. For example, the identifiedaction may be a mouse click or keyboard press indicating that a recordshould be open. In other instances, the identified action may include acondition or result that occurs in one or more processes. For example, arecord may be automatically opened when a call is received.

In one or more implementations, the action to open a new tab may beidentified in various ways. In some instances the action may beidentified by determining user input using one or more client-side webtechnologies, such as HTML or JavaScript®, to detect user interactionwith the user interface. In some instances, the action may be identifiedby receiving a message from the server (e.g., an HTTP message, an Ajaxmessage, etc.). For example, the server may send a message to thebrowser indicating that a call is being routed to the client machine.

In some implementations, identifying the action to open a new tab for arecord may include identifying the record itself. In some instances, anidentifier for the record may be determined when the action is detected.For example, the identifier may be included in a link clicked by a user.In other instances, an identifier for the record may be determined basedon cached information at the client and/or communication with theserver.

At 208, a determination is made as to whether the record tab is alreadyopen. In some implementations, the determination may be made based oninformation at the client machine. For example, a list of open tabs maybe maintained at the client machine, and an identifier associated withthe identified record may be compared against that list.

In some implementations, the determination as to whether the record tabis already open may be made in cooperation with the server. For example,the server may query a database to determine an identifier associatedwith the record. As another example, the server may maintain a list ofrecords opened at the client machine. The server may then return to theclient an indication as to whether the record tab is already open.

At 212, a determination is made as to whether to open the record in aprimary tab. In one or more implementations, a record (e.g., a databaserow) may be either a primary object (e.g., a workspace object) or asecondary object. For example, a customer account may be treated as aprimary object, while a case may be treated as a secondary object.

The determination as to whether to open the record in a primary tab maybe based upon whether the record represents a primary or workspaceableobject (e.g., an account), or a secondary object associated with aprimary object (e.g., a case associated with an account). When record isassociated with a workspace object, the record may be termed a “child”of the workspace “parent” object.

If the record is a workspace object, such as a customer account, thenthe record may open in a primary tab. If instead the record is asecondary object that is associated with a workspace object, such as acase that is associated with a customer account, then the record mayopen in a secondary tab.

If the record is a secondary object that is not associated with aworkspace object, such as a case for which an account has not yet beenopened, then the record may open in a primary tab. If the record is acustom object that does not have an assigned category or association,then the record may open as a primary tab. If a custom record or othersecondary object is opened in a primary tab, then the record's ownhighlight's panel layout may be used to display a highlights panel forthe workspace.

In some implementations, the determination 212 may be made at the clientmachine. For example, the client machine may maintain informationindicating certain record types that should open as primary or secondarytabs. In one or more implementations, the determination 212 may be madein conjunction with communication with the server. For example, theclient machine may transmit to the server a record type and/or recordidentifier associated with the record. The server may then conduct adatabase query and then return an indication as to whether to load therecord in a primary or secondary tab.

At 220, the primary tab ID for the parent record is identified. In someinstances, the primary tab ID may be identified at the server, forexample by querying a database after the record has been identified bythe client machine. In other instances, the primary tab ID may beidentified at the client machine, for example by consulting cached tabinformation stored at the client machine.

At 216, the record is retrieved from the server and opened in a newprimary tab. Retrieving the record may involve one or more databasequeries to collect data and/or layout information for display in some orall of the user interface components that may be associated with a tab,including main view information, contextual information, overview panelinformation, etc. Since the record is opened as a primary tab,highlights panel information may also be retrieved.

The retrieved information is then transmitted from the server to theclient machine. When the retrieved record information is received at theclient machine, the client machine opens the record in a new primarytab. The client machine may change focus to the new tab in the userinterface once the new tab is open. However, the context is maintainedso that other tabs that were previously open may be selected.

At 224, a determination is made as to whether the parent record can beopened. The parent record may not be available for opening if, forexample, the user lacks permission to open the parent record, the parentrecord does not exist, the parent record is invalid, etc. If the parentrecord is not available for opening, then the parent record may beopened in a new primary tab, as shown at 216.

In some instances, the determination as to whether the parent record canbe opened may be made on the client machine. For example, if the primarytab ID for the parent record is null or otherwise invalid, then theclient machine may determine that the parent record may not be openedwithout communicating with the server.

In some instances, the determination as to whether the parent record canbe opened may be made on the server. For example, the server maydetermine whether the user has permission to open the parent record bycomparing one or more permissions associated with the user's profile toone or more permissions required to open the parent record.

At 228, a determination is made as to whether the parent record tab isalready open. In some implementations, the determination may be madebased on information at the client machine. For example, a list of opentabs may be maintained at the client machine, and an identifierassociated with the parent record may be compared against that list.

In some implementations, the determination as to whether the record tabis already open may be made in cooperation with the server. For example,the server may maintain a list of records opened at the client machine.The server may then return to the client an indication as to whether theparent record tab is already open.

At 232, the parent record is retrieved from the server and opened as aprimary tab. Retrieving the parent record may involve one or moredatabase queries to collect data and/or layout information for displayin some or all of the user interface components that may be associatedwith a tab, including main view information, contextual information,overview panel information, etc. Since the parent record is opened as aprimary tab, highlights panel information may also be retrieved.

The retrieved record information is then transmitted from the server tothe client machine. When the retrieved record information is received atthe client machine, the client machine opens the parent record in a newprimary tab. The client machine may change focus to the new tab in theuser interface once the new tab is open. However, the context ismaintained so that other tabs that were previously open may be selected.

At 236, the record is retrieved from the server and opened in a newsubtab of the primary tab. Retrieving the record may involve one or moredatabase queries to collect data and/or layout information for displayin some or all of the user interface components that may be associatedwith a tab, including main view information, contextual information,overview panel information, etc.

The retrieved record information is then transmitted from the server tothe client machine. When the retrieved record information is received atthe client machine, the client machine opens the record in a new subtabof the primary tab. The client machine may change focus to the newsubtab in the user interface once the new subtab tab is open. However,the context is maintained so that other tabs that were previously openmay be selected.

In one or more implementations, a record tab may include a tab label. Atab label may include information associated with the page, such as thename and/or type of page being opened. For example, an account recordcalled Acme Systems may open with a tab labeled “Account: Acme Systems.”As another example, tabs for external pages may be labeled as “ExternalPage,” since page titles currently may not be retrieved from HTMLiframes. In some implementations, the tab label of a tab may change whenthe tab or a subtab changes (e.g., when a page is moved from detail modeto edit mode).

In one or more implementations, tab labels that exceed the tab size maybe truncated. For example, excess characters may be replaced by anellipsis. In some implementations, tabs may be dynamically resizedaccording to the number of tabs in existence.

In one or more implementations, one or more of the operations shown inFIG. 2 may be performed at the client machine, at the server, or using aclient/server combination. Where an operation is performed may be basedon where information is located. For example, the client machine maymaintain cached information that allows the client machine to performone or more operations without communicating with the server. However,cached information may in some instances be insufficient to perform anoperation without server interaction.

In some implementations, one or more of the operations shown in FIG. 2may be performed in a different order than is shown. For example, two ormore operations that involve communication between the client machineand server may be combined into fewer operations in order to reduce theburden on the server and/or reduce client-side delays caused bycommunicating with the server. For example, operations 212 and 216 maybe combined into a single client-server interaction in some instances.

FIG. 3A shows a system diagram of an example of architectural componentsof an on-demand service environment, in accordance with someimplementations.

A client machine located in the cloud 304 (or Internet) may communicatewith the on-demand service environment via one or more edge routers 308and 312. The edge routers may communicate with one or more core switches320 and 324 via firewall 316. The core switches may communicate with aload balancer 328, which may distribute server load over different pods,such as the pods 340 and 344. The pods 340 and 344, which may eachinclude one or more servers and/or other computing resources, mayperform data processing and other operations used to provide on-demandservices. Communication with the pods may be conducted via pod switches332 and 336. Components of the on-demand service environment maycommunicate with a database storage system 356 via a database firewall348 and a database switch 352.

As shown in FIGS. 3A and 3B, accessing an on-demand service environmentmay involve communications transmitted among a variety of differenthardware and/or software components. Further, the on-demand serviceenvironment 300 is a simplified representation of an actual on-demandservice environment. For example, while only one or two devices of eachtype are shown in FIGS. 3A and 3B, some implementations of an on-demandservice environment may include anywhere from one to many devices ofeach type. Also, the on-demand service environment need not include eachdevice shown in FIGS. 3A and 3B, or may include additional devices notshown in FIGS. 3A and 3B.

Moreover, one or more of the devices in the on-demand serviceenvironment 300 may be implemented on the same physical device or ondifferent hardware. Some devices may be implemented using hardware or acombination of hardware and software. Thus, terms such as “dataprocessing apparatus,” “machine,” “server”, “computing device” and“device” as used herein are not limited to a single hardware device, butrather include any hardware and software configured to provide thedescribed functionality.

The cloud 304 is intended to refer to a data network or plurality ofdata networks, often including the Internet. Client machines located inthe cloud 304 may communicate with the on-demand service environment toaccess services provided by the on-demand service environment. Forexample, client machines may access the on-demand service environment toretrieve, store, edit, and/or process information.

In some implementations, the edge routers 308 and 312 route packetsbetween the cloud 304 and other components of the on-demand serviceenvironment 300. The edge routers 308 and 312 may employ the BorderGateway Protocol (BGP). The BGP is the core routing protocol of theInternet. The edge routers 308 and 312 may maintain a table of IPnetworks or ‘prefixes’ which designate network reachability amongautonomous systems on the Internet.

In one or more implementations, the firewall 316 may protect the innercomponents of the on-demand service environment 300 from Internettraffic. The firewall 316 may block, permit, or deny access to the innercomponents of the on-demand service environment 300 based upon a set ofrules and other criteria. The firewall 316 may act as one or more of apacket filter, an application gateway, a stateful filter, a proxyserver, or any other type of firewall.

In some implementations, the core switches 320 and 324 are high-capacityswitches that transfer packets within the on-demand service environment300. The core switches 320 and 324 may be configured as network bridgesthat quickly route data between different components within theon-demand service environment. In some implementations, the use of twoor more core switches 320 and 324 may provide redundancy and/or reducedlatency.

In some implementations, the pods 340 and 344 may perform the core dataprocessing and service functions provided by the on-demand serviceenvironment. Each pod may include various types of hardware and/orsoftware computing resources. An example of the pod architecture isdiscussed in greater detail with reference to FIG. 3B.

In some implementations, communication between the pods 340 and 344 maybe conducted via the pod switches 332 and 336. The pod switches 332 and336 may facilitate communication between the pods 340 and 344 and clientmachines located in the cloud 304, for example via core switches 320 and324. Also, the pod switches 332 and 336 may facilitate communicationbetween the pods 340 and 344 and the database storage 356.

In some implementations, the load balancer 328 may distribute workloadbetween the pods 340 and 344. Balancing the on-demand service requestsbetween the pods may assist in improving the use of resources,increasing throughput, reducing response times, and/or reducingoverhead. The load balancer 328 may include multilayer switches toanalyze and forward traffic.

In some implementations, access to the database storage 356 may beguarded by a database firewall 348. The database firewall 348 may act asa computer application firewall operating at the database applicationlayer of a protocol stack. The database firewall 348 may protect thedatabase storage 356 from application attacks such as structure querylanguage (SQL) injection, database rootkits, and unauthorizedinformation disclosure.

In some implementations, the database firewall 348 may include a hostusing one or more forms of reverse proxy services to proxy trafficbefore passing it to a gateway router. The database firewall 348 mayinspect the contents of database traffic and block certain content ordatabase requests. The database firewall 348 may work on the SQLapplication level atop the TCP/IP stack, managing applications'connection to the database or SQL management interfaces as well asintercepting and enforcing packets traveling to or from a databasenetwork or application interface.

In some implementations, communication with the database storage system356 may be conducted via the database switch 352. The multi-tenantdatabase system 356 may include more than one hardware and/or softwarecomponents for handling database queries. Accordingly, the databaseswitch 352 may direct database queries transmitted by other componentsof the on-demand service environment (e.g., the pods 340 and 344) to thecorrect components within the database storage system 356.

In some implementations, the database storage system 356 is an on-demanddatabase system shared by many different organizations. The on-demanddatabase system may employ a multi-tenant approach, a virtualizedapproach, or any other type of database approach. An on-demand databasesystem is discussed in greater detail with reference to FIGS. 4 and 5.

FIG. 3B shows a system diagram further illustrating an example ofarchitectural components of an on-demand service environment, inaccordance with some implementations. The pod 344 may be used to renderservices to a user of the on-demand service environment 300.

In some implementations, each pod may include a variety of serversand/or other systems. The pod 344 includes one or more content batchservers 364, content search servers 368, query servers 372, file forceservers 376, access control system (ACS) servers 380, batch servers 384,and app servers 388. Also, the pod 344 includes database instances 390,quick file systems (QFS) 392, and indexers 394. In one or moreimplementations, some or all communication between the servers in thepod 344 may be transmitted via the switch 336.

In some implementations, the application servers 388 may include ahardware and/or software framework dedicated to the execution ofprocedures (e.g., programs, routines, scripts) for supporting theconstruction of applications provided by the on-demand serviceenvironment 300 via the pod 344. Some such procedures may includeoperations for providing the services described herein.

The content batch servers 364 may requests internal to the pod. Theserequests may be long-running and/or not tied to a particular customer.For example, the content batch servers 364 may handle requests relatedto log mining, cleanup work, and maintenance tasks.

The content search servers 368 may provide query and indexer functions.For example, the functions provided by the content search servers 368may allow users to search through content stored in the on-demandservice environment.

The Fileforce servers 376 may manage requests information stored in theFileforce storage 378. The Fileforce storage 378 may store informationsuch as documents, images, and basic large objects (BLOBs). By managingrequests for information using the Fileforce servers 376, the imagefootprint on the database may be reduced.

The query servers 372 may be used to retrieve information from one ormore file systems. For example, the query system 372 may receiverequests for information from the app servers 388 and then transmitinformation queries to the NFS 396 located outside the pod.

The pod 344 may share a database instance 390 configured as amulti-tenant environment in which different organizations share accessto the same database. Additionally, services rendered by the pod 344 mayrequire various hardware and/or software resources. In someimplementations, the ACS servers 380 may control access to data,hardware resources, or software resources.

In some implementations, the batch servers 384 may process batch jobs,which are used to run tasks at specified times. Thus, the batch servers384 may transmit instructions to other servers, such as the app servers388, to trigger the batch jobs.

In some implementations, the QFS 392 may be an open source file systemavailable from Sun Microsystems® of Santa Clara, Calif. The QFS mayserve as a rapid-access file system for storing and accessinginformation available within the pod 344. The QFS 392 may support somevolume management capabilities, allowing many disks to be groupedtogether into a file system. File system metadata can be kept on aseparate set of disks, which may be useful for streaming applicationswhere long disk seeks cannot be tolerated. Thus, the QFS system maycommunicate with one or more content search servers 368 and/or indexers394 to identify, retrieve, move, and/or update data stored in thenetwork file systems 396 and/or other storage systems.

In some implementations, one or more query servers 372 may communicatewith the NFS 396 to retrieve and/or update information stored outside ofthe pod 344. The NFS 396 may allow servers located in the pod 344 toaccess information to access files over a network in a manner similar tohow local storage is accessed.

In some implementations, queries from the query servers 322 may betransmitted to the NFS 396 via the load balancer 320, which maydistribute resource requests over various resources available in theon-demand service environment. The NFS 396 may also communicate with theQFS 392 to update the information stored on the NFS 396 and/or toprovide information to the QFS 392 for use by servers located within thepod 344.

In some implementations, the pod may include one or more databaseinstances 390. The database instance 390 may transmit information to theQFS 392. When information is transmitted to the QFS, it may be availablefor use by servers within the pod 344 without requiring an additionaldatabase call.

In some implementations, database information may be transmitted to theindexer 394. Indexer 394 may provide an index of information availablein the database 390 and/or QFS 392. The index information may beprovided to file force servers 376 and/or the QFS 392.

FIG. 4 shows a system diagram illustrating an example of thearchitecture of a multitenant database environment, in accordance withsome implementations.

Environment 410 includes an on-demand database service 416. User system412 may be any client machine or system that is used by a user to accessa database system. For example, any of user systems 412 can be ahandheld computing device, a mobile phone, a laptop computer, a workstation, and/or a network of computing devices. As illustrated in FIGS.4 and 5, user systems 412 might interact via a network 414 with theon-demand database service 416.

An on-demand database service, such as system 416, is a database systemthat is made available to outside users that do not need to necessarilybe concerned with building and/or maintaining the database system, butinstead may be available for their use when the users need the databasesystem (e.g., on the demand of the users). Some on-demand databaseservices may store information from one or more tenants stored intotables of a common database image to form a multi-tenant database system(MTS).

Accordingly, “on-demand database service 416” and “system 416” will beused interchangeably herein. A database image may include one or moredatabase objects. A relational database management system (RDBMS) or theequivalent may execute storage and retrieval of information against thedatabase object(s). Application platform 418 may be a framework thatallows the applications of system 416 to run, such as the hardwareand/or software, e.g., the operating system. In an implementation,on-demand database service 416 may include an application platform 418that enables creation, managing and executing one or more applicationsdeveloped by the provider of the on-demand database service, usersaccessing the on-demand database service via user systems 412, or thirdparty application developers accessing the on-demand database servicevia user systems 412.

One arrangement for elements of system 416 is shown in FIG. 4, includinga network interface 420, application platform 418, tenant data storage422 for tenant data 423, system data storage 424 for system data 425accessible to system 416 and possibly multiple tenants, program code 426for implementing various functions of system 416, and a process space428 for executing MTS system processes and tenant-specific processes,such as running applications as part of an application hosting service.Additional processes that may execute on system 416 include databaseindexing processes.

The users of user systems 412 may differ in their respective capacities,and the capacity of a particular user system 412 might be entirelydetermined by permissions (permission levels) for the current user. Forexample, where a call center agent is using a particular user system 412to interact with system 416, the user system 412 has the capacitiesallotted to that call center agent. However, while an administrator isusing that user system to interact with system 416, that user system hasthe capacities allotted to that administrator. In systems with ahierarchical role model, users at one permission level may have accessto applications, data, and database information accessible by a lowerpermission level user, but may not have access to certain applications,database information, and data accessible by a user at a higherpermission level. Thus, different users may have different capabilitieswith regard to accessing and modifying application and databaseinformation, depending on a user's security or permission level.

Network 414 is any network or combination of networks of devices thatcommunicate with one another. For example, network 414 can be any one orany combination of a LAN (local area network), WAN (wide area network),telephone network, wireless network, point-to-point network, starnetwork, token ring network, hub network, or other appropriateconfiguration. As the most common type of computer network in currentuse is a TCP/IP (Transfer Control Protocol and Internet Protocol)network (e.g., the Internet), that network will be used in many of theexamples herein. However, it should be understood that the networks usedin some implementations are not so limited, although TCP/IP is afrequently implemented protocol.

User systems 412 might communicate with system 416 using TCP/IP and, ata higher network level, use other common Internet protocols tocommunicate, such as HTTP, FTP, AFS, WAP, etc. In an example where HTTPis used, user system 412 might include an HTTP client commonly referredto as a “browser” for sending and receiving HTTP messages to and from anHTTP server at system 416. Such an HTTP server might be implemented asthe sole network interface between system 416 and network 414, but othertechniques might be used as well or instead. In some implementations,the interface between system 416 and network 414 includes load sharingfunctionality, such as round-robin HTTP request distributors to balanceloads and distribute incoming HTTP requests evenly over a plurality ofservers. At least as for the users that are accessing that server, eachof the plurality of servers has access to the MTS' data; however, otheralternative configurations may be used instead.

In one implementation, system 416, shown in FIG. 4, implements aweb-based customer relationship management (CRM) system such as theservice cloud console. For example, in one implementation, system 416includes application servers configured to implement and execute CRMsoftware applications as well as provide related data, code, forms, webpages and other information to and from user systems 412 and to storeto, and retrieve from, a database system related data, objects, andWebpage content. With a multi-tenant system, data for multiple tenantsmay be stored in the same physical database object, however, tenant datatypically is arranged so that data of one tenant is kept logicallyseparate from that of other tenants so that one tenant does not haveaccess to another tenant's data, unless such data is expressly shared.In certain implementations, system 416 implements applications otherthan, or in addition to, a CRM application. For example, system 416 mayprovide tenant access to multiple hosted (standard and custom)applications. User (or third party developer) applications, which may ormay not include CRM, may be supported by the application platform 418,which manages creation, storage of the applications into one or moredatabase objects and executing of the applications in a virtual machinein the process space of the system 416.

Each user system 412 could include a desktop personal computer,workstation, laptop, PDA, cell phone, or any wireless access protocol(WAP) enabled device or any other computing device capable ofinterfacing directly or indirectly to the Internet or other networkconnection. User system 412 typically runs an HTTP client, e.g., abrowsing program, such as Microsoft's Internet Explorer® browser,Mozilla's Firefox® browser, Opera's browser, or a WAP-enabled browser inthe case of a cell phone, PDA or other wireless device, or the like,allowing a user (e.g., subscriber of the multi-tenant database system)of user system 412 to access, process and view information, pages andapplications available to it from system 416 over network 414.

Each user system 412 also typically includes one or more user interfacedevices, such as a keyboard, a mouse, trackball, touch pad, touchscreen, pen or the like, for interacting with a graphical user interface(GUI) provided by the browser on a display (e.g., a monitor screen, LCDdisplay, etc.) in conjunction with pages, forms, applications and otherinformation provided by system 416 or other systems or servers. Forexample, the user interface device can be used to access data andapplications hosted by system 416, and to perform searches on storeddata, and otherwise allow a user to interact with various GUI pages thatmay be presented to a user. As discussed above, implementations aresuitable for use with the Internet, which refers to a specific globalinternetwork of networks. However, it should be understood that othernetworks can be used instead of the Internet, such as an intranet, anextranet, a virtual private network (VPN), a non-TCP/IP based network,any LAN or WAN or the like.

According to one implementation, each user system 412 and all of itscomponents are operator configurable using applications, such as abrowser, including computer code run using a central processing unitsuch as an Intel Pentium® processor or the like. Similarly, system 416(and additional instances of an MTS, where more than one is present) andall of their components might be operator configurable usingapplication(s) including computer code to run using a central processingunit such as processor system 417, which may include an Intel Pentium®processor or the like, and/or multiple processor units.

A computer program product implementation includes a machine-readablestorage medium (media) having instructions stored thereon/in which canbe used to program a computer to perform any of the processes of theimplementations described herein. Computer code for operating andconfiguring system 416 to intercommunicate and to process web pages,applications and other data and media content as described herein arepreferably downloaded and stored on a hard disk, but the entire programcode, or portions thereof, may also be stored in any other volatile ornon-volatile memory medium or device, such as a ROM or RAM, or providedon any media capable of storing program code, such as any type ofrotating media including floppy disks, optical discs, digital versatiledisk (DVD), compact disk (CD), microdrive, and magneto-optical disks,and magnetic or optical cards, nanosystems (including molecular memoryICs), or any type of media or device suitable for storing instructionsand/or data. Additionally, the entire program code, or portions thereof,may be transmitted and downloaded from a software source over atransmission medium, e.g., over the Internet, or from another server, ortransmitted over any other conventional network connection (e.g.,extranet, VPN, LAN, etc.) using any communication medium and protocols(e.g., TCP/IP, HTTP, HTTPS, Ethernet, etc.). It will also be appreciatedthat computer code for implementing implementations can be implementedin any programming language that can be executed on a client systemand/or server or server system such as, for example, C, C++, HTML, anyother markup language, Java™, JavaScript®, ActiveX®, any other scriptinglanguage, such as VBScript, and many other programming languages as arewell known may be used. (Java™ is a trademark of Sun Microsystems®,Inc.).

According to one implementation, each system 416 is configured toprovide web pages, forms, applications, data and media content to user(client) systems 412 to support the access by user systems 412 astenants of system 416. As such, system 416 provides security mechanismsto keep each tenant's data separate unless the data is shared. If morethan one MTS is used, they may be located in close proximity to oneanother (e.g., in a server farm located in a single building or campus),or they may be distributed at locations remote from one another (e.g.,one or more servers located in city A and one or more servers located incity B). As used herein, each MTS could include logically and/orphysically connected servers distributed locally or across one or moregeographic locations. Additionally, the term “server” is meant toinclude a computer system, including processing hardware and processspace(s), and an associated storage system and database application(e.g., OODBMS or RDBMS) as is well known in the art.

It should also be understood that “server system” and “server” are oftenused interchangeably herein. Similarly, the database object describedherein can be implemented as single databases, a distributed database, acollection of distributed databases, a database with redundant online oroffline backups or other redundancies, etc., and might include adistributed database or storage network and associated processingintelligence.

FIG. 5 shows a system diagram further illustrating an example of thearchitecture of a multitenant database environment, in accordance withsome implementations. FIG. 5 shows that user system 412 may includeprocessor system 412A, memory system 412B, input system 412C, and outputsystem 412D. FIG. 5 shows network 414 and system 416. FIG. 5 also showsthat system 416 may include tenant data storage 422, tenant data 423,system data storage 424, system data 425, User Interface (UI) 530,Application Program Interface (API) 532, PL/SOQL 534, save routines 536,application setup mechanism 538, applications servers 5001-500N, systemprocess space 502, tenant process spaces 504, tenant management processspace 510, tenant storage area 512, user storage 514, and applicationmetadata 516. In other implementations, environment 410 may not have thesame elements as those listed above and/or may have other elementsinstead of, or in addition to, those listed above.

User system 412, network 414, system 416, tenant data storage 422, andsystem data storage 424 were discussed above in FIG. 4. Regarding usersystem 412, processor system 412A may be any combination of processors.Memory system 412B may be any combination of one or more memory devices,short term, and/or long term memory. Input system 412C may be anycombination of input devices, such as keyboards, mice, trackballs,scanners, cameras, and/or interfaces to networks. Output system 412D maybe any combination of output devices, such as monitors, printers, and/orinterfaces to networks. As shown by FIG. 5, system 416 may include anetwork interface 420 (of FIG. 4) implemented as a set of HTTPapplication servers 500, an application platform 418, tenant datastorage 422, and system data storage 424. Also shown is system processspace 502, including individual tenant process spaces 504 and a tenantmanagement process space 510. Each application server 500 may beconfigured to tenant data storage 422 and the tenant data 423 therein,and system data storage 424 and the system data 425 therein to serverequests of user systems 412. The tenant data 423 might be divided intoindividual tenant storage areas 512, which can be either a physicalarrangement and/or a logical arrangement of data. Within each tenantstorage area 512, user storage 514 and application metadata 516 might besimilarly allocated for each user. For example, a copy of a user's mostrecently used (MRU) items might be stored to user storage 514.Similarly, a copy of MRU items for an entire organization that is atenant might be stored to tenant storage area 512. A UI 530 provides auser interface and an API 532 provides an application programmerinterface to system 416 resident processes to users and/or developers atuser systems 412. The tenant data and the system data may be stored invarious databases, such as Oracle™ databases.

Application platform 418 includes an application setup mechanism 538that supports application developers' creation and management ofapplications, which may be saved as metadata into tenant data storage422 by save routines 536 for execution by subscribers as tenant processspaces 504 managed by tenant management process 510 for example.Invocations to such applications may be coded using PL/SOQL 34 thatprovides a programming language style interface extension to API 532. Adetailed description of some PL/SOQL language implementations isdiscussed in commonly assigned U.S. Pat. No. 7,730,478, titled METHODAND SYSTEM FOR ALLOWING ACCESS TO DEVELOPED APPLICATIONS VIA AMULTI-TENANT ON-DEMAND DATABASE SERVICE, by Craig Weissman, filed Sep.21, 2007, which is hereby incorporated by reference in its entirety andfor all purposes. Invocations to applications may be detected by systemprocesses, which manage retrieving application metadata 516 for thesubscriber making the invocation and executing the metadata as anapplication in a virtual machine.

Each application server 500 may be communicably coupled to databasesystems, e.g., having access to system data 425 and tenant data 423, viaa different network connection. For example, one application server 5001might be coupled via the network 414 (e.g., the Internet), anotherapplication server 500N-1 might be coupled via a direct network link,and another application server 500N might be coupled by yet a differentnetwork connection. Transfer Control Protocol and Internet Protocol(TCP/IP) are typical protocols for communicating between applicationservers 500 and the database system. However, other transport protocolsmay be used to optimize the system depending on the network interconnectused.

In certain implementations, each application server 500 is configured tohandle requests for any user associated with any organization that is atenant. Because it is desirable to be able to add and remove applicationservers from the server pool at any time for any reason, there ispreferably no server affinity for a user and/or organization to aspecific application server 500. In one implementation, therefore, aninterface system implementing a load balancing function (e.g., an F5Big-IP load balancer) is communicably coupled between the applicationservers 500 and the user systems 412 to distribute requests to theapplication servers 500. In one implementation, the load balancer uses aleast connections algorithm to route user requests to the applicationservers 500. Other examples of load balancing algorithms, such as roundrobin and observed response time, also can be used. For example, incertain implementations, three consecutive requests from the same usercould hit three different application servers 500, and three requestsfrom different users could hit the same application server 500. In thismanner, system 416 is multi-tenant, wherein system 416 handles storageof, and access to, different objects, data and applications acrossdisparate users and organizations.

As an example of storage, one tenant might be a company that employs asales force where each call center agent uses system 416 to manage theirsales process. Thus, a user might maintain contact data, leads data,customer follow-up data, performance data, goals and progress data,etc., all applicable to that user's personal sales process (e.g., intenant data storage 422). In an example of a MTS arrangement, since allof the data and the applications to access, view, modify, report,transmit, calculate, etc., can be maintained and accessed by a usersystem having nothing more than network access, the user can manage hisor her sales efforts and cycles from any of many different user systems.For example, if a call center agent is visiting a customer and thecustomer has Internet access in their lobby, the call center agent canobtain critical updates as to that customer while waiting for thecustomer to arrive in the lobby.

While each user's data might be separate from other users' dataregardless of the employers of each user, some data might beorganization-wide data shared or accessible by a plurality of users orall of the users for a given organization that is a tenant. Thus, theremight be some data structures managed by system 416 that are allocatedat the tenant level while other data structures might be managed at theuser level. Because an MTS might support multiple tenants includingpossible competitors, the MTS should have security protocols that keepdata, applications, and application use separate. Also, because manytenants may opt for access to an MTS rather than maintain their ownsystem, redundancy, up-time, and backup are additional functions thatmay be implemented in the MTS. In addition to user-specific data andtenant specific data, system 416 might also maintain system level datausable by multiple tenants or other data. Such system level data mightinclude industry reports, news, postings, and the like that are sharableamong tenants.

In certain implementations, user systems 412 (which may be clientmachines/systems) communicate with application servers 500 to requestand update system-level and tenant-level data from system 416 that mayrequire sending one or more queries to tenant data storage 422 and/orsystem data storage 424. System 416 (e.g., an application server 500 insystem 416) automatically generates one or more SQL statements (e.g.,SQL queries) that are designed to access the desired information. Systemdata storage 424 may generate query plans to access the requested datafrom the database.

Each database can generally be viewed as a collection of objects, suchas a set of logical tables, containing data fitted into predefinedcategories. A “table” is one representation of a data object, and may beused herein to simplify the conceptual description of objects and customobjects according to some implementations. It should be understood that“table” and “object” may be used interchangeably herein. Each tablegenerally contains one or more data categories logically arranged ascolumns or fields in a viewable schema. Each row or record of a tablecontains an instance of data for each category defined by the fields.For example, a CRM database may include a table that describes acustomer with fields for basic contact information such as name,address, phone number, fax number, etc. Another table might describe apurchase order, including fields for information such as customer,product, sale price, date, etc. In some multi-tenant database systems,standard entity tables might be provided for use by all tenants. For CRMdatabase applications, such standard entities might include tables foraccount, contact, lead, and opportunity data, each containingpre-defined fields. It should be understood that the word “entity” mayalso be used interchangeably herein with “object” and “table”.

In some multi-tenant database systems, tenants may be allowed to createand store custom objects, or they may be allowed to customize standardentities or objects, for example by creating custom fields for standardobjects, including custom index fields. U.S. Pat. No. 7,779,039, titledCUSTOM ENTITIES AND FIELDS IN A MULTI-TENANT DATABASE SYSTEM, byWeissman, et al., and which is hereby incorporated by reference in itsentirety and for all purposes, teaches systems and methods for creatingcustom objects as well as customizing standard objects in a multi-tenantdatabase system. In some implementations, for example, all custom entitydata rows are stored in a single multi-tenant physical table, which maycontain multiple logical tables per organization. In someimplementations, multiple “tables” for a single customer may actually bestored in one large table and/or in the same table as the data of othercustomers.

The implementations disclosed herein may include a cross-domain APIsituated at a client machine that allows pages served from externaldomains to perform certain actions, such as exchanging information withone another, within a web browser program running on the client machine.These pages may be referred to as “third party pages.” FIGS. 6A and 6Bshow flow diagrams illustrating interactions of third party pages, inaccordance with one or more implementations. In one or moreimplementations, this cross-domain API may be referred to as a servicecloud console integration toolkit.

Call centers that use the service cloud console may have integrations tothird party systems, such as billing systems, shipping systems,accounting systems, etc. The service cloud console may provide aninterface that allows agents access to one or more of theseapplications. In some implementations, one or more of these third partyapplications may participate in the tabbed model provided through theservice cloud console.

Because communication between frames from different domains presents asecurity risk within the browsers, this functionality is explicitlyrestricted in some modern browsers. In other modern browsers, however,cross-domain communication has been addressed, for instance, in HTML 5(available from W3.org at http://www.w3.org/TR/htm15/comms.html) withthe postMessage framework. However, HTML 5 is currently supported inonly a limited number of browsers, such as Internet Explorer 8, Firefox3, and Opera 9.

In some implementations, the cross-domain API may be used to facilitateintegration with third party pages within Salesforce.com® itself. Forexample, VisualForce™ pages may be served from a different domain thanthe service cloud console.

Given the potential security concerns, it may be desirable to avoidexposing the ability for a third-party domain to directly perform datamanipulation. For example, in Salesforce.com® it may be possible to openan edit page, make modifications to an object, and save it, all byopening a single URL with a set of parameters in the query string.However, this type of operation may not be permitted by the cross-domainAPI, as it could open up a means for attackers to modify data withoutthe user's knowledge or consent.

The third party page communication methods shown in FIGS. 6A and 6B maybe used to facilitate secure cross-domain communication. These methodsmay be run in a web browser at a client machine in communication withone or more servers that provide data to the browser. However, some orall of the individual processing steps shown in FIGS. 6A and 6B may beperformed without communication with the server. Thus, cross-domaincommunications may be facilitated without requiring the additionallatency or computational burdens that would exist if cross-domaincommunications were accomplished using a proxy or other type of servercommunication.

In one implementation, in 604, a service cloud console application fromthe data provider is loaded from a first domain, such aswww.salesforce.com. The console application may be loaded by sendinginstructions from one or more data provider servers hosting the firstdomain to a web browser at a client machine. When the consoleapplication is loaded, records served from the first domain may bevisible in the console application. For example, one or more records maybe opened using a record open method, as shown in FIG. 2.

In 608, a third party web page is loaded from a second domain, forinstance, from phone system 68, in a portion of a user interface alsodisplaying the console application. In some implementations, the thirdparty web page may be loaded as a primary or secondary tab within theconsole application. The third party web page may also be automaticallyloaded in response to receiving data from the console application. Forexample, a first object record may include a link to accountinginformation visible through a third party web page. When the link isclicked, the third party web page is loaded.

In some implementations, the first domain is controlled by a dataprovider, e.g., salesforce.com®, while the second domain may becontrolled by a different entity, such as the phone provider. Forexample, the console application may be loaded from a first domaincontrolled by salesforce.com®, while the third party page is loaded froma second domain controlled by a third party service providerunaffiliated with the service provider controlling the first domain

In 612, the console application is configured to listen to events from afirst set of safe domains. The first set of safe domains identifies theone or more trusted domains from which the console application maysafely accept cross-domain messages. In some implementations, the firstset of safe domains may be limited to a particular group of domains,such as those provided by the data provider of the console application.The first set of safe domains may also include domains identified astrusted, such as the second domain associated with a third party serviceprovider system.

In some implementations, wildcards may be used to identify groups ofdomains using a single string. For example, the first set of safedomains may include domains such as na1.force.com, *.na2.force.com,and/or *.salesforce.com.

In 616, the third party page may detect or generate an event of sometype, such as the receipt of phone event information from some source,as described above. The detected event may include any type ofoccurrence that causes cross-domain communication. In someimplementations, the event may be a scripting event triggered directlyby a user action, such as clicking a link or button within the thirdparty page. Alternately, or additionally, the event may be generated bycode running within the third party page that identifies a triggeringcondition.

In 620, the event triggers a message that is sent to the consoleapplication. The message may include a JavaScript® event message, orother type of event message. The message may be sent to a JavaScript®Event Listener operating in the console application served from thefirst domain. Alternately, or additionally, a different type ofscripting language may be used, such as VBScript.

When the event message is received, the console application identifiesthe domain from which the event message was sent (i.e. the seconddomain), as shown at 624. The domain may be identified by retrieving avalue associated with the event message. After the second domain isidentified as the source of the event, the second domain is compared tothe first set of safe domains, as shown at 628.

As shown at 632, if the second domain is not within the first set ofsafe domains, then the message is ignored. In this case, the seconddomain has not been identified as a “safe” domain from which to receivemessages. By only accepting messages sent from an identified subset ofdomains, the security risks inherent in cross-domain communications maybe mitigated.

In some implementations, receiving a cross-domain event message from athird party domain not in the first set of safe domains may cause one ormore security or logging actions to be taken. For example, the eventmessage may be logged in a security record to help identify unauthorizedattempts to access the service cloud console application.

As shown at 636, the event message is processed if the second domain iswithin the first set of safe domains. The event message may be processedaccording to one or more event handlers in the console application.

In some implementations, even domains included in the first set of safedomains may be limited to triggering particular actions or types ofactions within the console application, in order to provide furtherprotection against unauthorized access. Examples of such actions arediscussed below. However, different implementations may allow variousactions or types of actions in response to an event message.

Regardless of whether the event message is processed, the service cloudconsole may continue monitoring for additional messages transmitted fromthird party domains. Continual monitoring for cross-domain eventmessages may be accomplished using, for example, an Observer designpattern. Thus, the third party page may be able to send messages to theservice cloud console, while the security of the console application ismaintained.

FIG. 6B shows a complementary third party page communication method Bfor transmitting messages from the console application to a third partypage. The method shown in FIG. 6B is similar to the method shown in FIG.6A in some respects, with like reference numerals indicating likeoperations.

In some implementations, a different set of safe domains may beidentified at 662 than at 612. For example, the second set of safedomains may be limited to domains associated with the service cloudconsole (e.g., *.force.com, *.salesforce.com), while the first set ofsafe domains may include one or more domains associated with third partyservice providers. By using different sets of safe domains, the securityof the third party pages may be maintained because the third party pagesmay not be operable to communicate with each other.

In 666, an event within the console application is detected, similar to616. In 670, an event message from the console application iscommunicated to the third party page, similar to 620. In someimplementations, a different set of actions or types of actions may beallowed in response to receiving an event message from an accepteddomain, as shown at 686. In both figures, the set of allowable actionsor types of actions may be strategically determined based on securityconcerns and the type of cross-domain communication that is needed tofacilitate integration.

In some implementations, the methods shown in FIGS. 6A and 6B may beperformed concurrently, thus allowing for secure cross-domain two-waycommunication between the console application and the third party page.Alternately, one of the methods shown in FIGS. 6A and 6B may be omittedso that only one-way cross-domain communication is allowed.

The cross-domain API is described with reference to a pseudocodeimplementation according to some implementations. However, thepseudocode is provided only as an example, and some implementations mayemploy a different implementation. For example, cross-domain API methodsmay be specified using some methods, method names, parameters, and/orparameter names (e.g., method(parameter1:type,parameter2:type):returntype). However, different methods, method names,parameters, and/or parameters names may be used in differentimplementations. As another example, at least part of the cross-domainAPI pseudocode here may appear as methods that return valuessynchronously. However, some implementations may include one or moremethods that return values asynchronously (e.g., via a callback method).

Developers may be able to import one or more libraries into variouspages, but some methods within these libraries may be prevented fromoperating unless the pages are run in a designated context.

Third party pages may have the ability to open primary tabs, subtabs, orboth. Primary tabs and subtabs opened from third party pages may follownavigation rules similar to standard pages. For example, duplicate pagesmay not be allowed by default. However, developers may be permitted toallow duplicate pages. As another example, third party pages may behavewith back, forward, and/or refresh buttons in a manner similar tostandard pages.

A page may only be able to manipulate itself and the tabs which it hasopened itself. If a VisualForce™ page is embedded on a standard page, itmay be able to manipulate the tab in which it is contained.

Workspace Objects

This section describes properties of workspace objects in one or moreimplementations.

In one or more implementations, an administrator may map a field on anobject to a workspaceable object using a workspace driver field. When anobject has a field configured in this way, it may become a subordinateobject. In this case, the object may only open in the workspace of theobject to which it is subordinate. Each object may be limited to oneworkspace driver field.

For example, one custom object may be a bill. A bill may have fieldssuch as amount (a currency), account (a lookup to account), and contact(a lookup to contact). One of these fields, or the bill itself, may bethe workspace driver. If account is set as the workspace driver field,then when opening a bill, the account will appear in the workspace tab,and the bill will appear as a subtab.

In one or more implementations, almost any object may be a workspaceobject. A workspace driver field may be used to define what workspace anobject will open in if not its own. Those driver fields may beselectable from the set of lookup relationships on a given object. Anyof an object's relationships may be available in this list.

Despite the existence of a workspace driver field, an object may open inits own workspace if it happens to be orphaned. For example, a caseobject may be configured such that the parent account is its workspaceobject, but the user may open a case which is orphaned, (i.e. its parentaccount is null). In this event, the case may open in its own workspace,even though under normal circumstances cases don't do so.

In one or more implementations, each objects have a highlights panellayout. If no highlights panel is defined for an object, its mini viewlayout may be used by default. This layout may be specified by the samemechanism used by the “deal view.”

In one or more implementations, only non-setup entities may be includedin the metadata allowing end users to choose their workspace properties.Setup entities like user may implicitly be configured as “Opens InItself”

In one or more implementations, VisualForce™ pages may be configurableas workspaceable pages or as subordinate objects. In the event that aVisualForce™ page is workspaceable, it may be allowed to omit thehighlights panel.

In one or more implementations, objects selected from a subtab may staywithin the context of that workspace. For example, suppose contact is aworkspaceable object and an account is open. A contact opened from theaccount details section may open as a subtab under the account and notin its own contact workspace. Even though contact is a workspaceableobject, it may be opened in the context of an account. In someimplementations, a user may drag the contact tab up to workspace bar tomake it its own workspace and/or drag one or more workspaces intosubtabs.

Publisher: Batch Publish and Next

FIG. 9 shows a flowchart of an example of a computer implemented method900 for composing and batch publishing feed items in a user interface ina feed-based interaction context, in accordance with someimplementations. FIG. 9 is described with references to the examples ofFIGS. 12-15.

In FIG. 9, at block 902, a computing device provides a first prompt fordisplay in a first user interface component of the user interface, thefirst prompt being associated with a first action. In someimplementations, the information entered in the first prompt may be usedto perform a first action, such as sending an email, attaching anarticle, and composing an internal note.

In FIG. 9, at block 904, the computing device performing method 900receives feed item data for a first feed item associated with the firstaction. The feed item data may be received at a first prompt displayedin the first user interface component. The first user interfacecomponent may be configured to display unpublished feed items. The userinterface may include a second user interface component that isconfigured to display published feed items.

In some implementations, the feed item may be an email to a customer, aninternal note, a flag, a status change, an attachment, a comment, asocial media message, a calendar item, or the like. The feed item may beany message that may be displayed or published in a feed. The first userinterface component may display one or more unpublished feed items ofdifferent types.

FIG. 12 shows an example of a graphical user interface (GUI) including apresentation of a user interface for publishing feed items, inaccordance with one or more implementations. FIG. 12 illustrates anexample of a Service Console page where an agent is presented with afirst user interface component 1210 in which unpublished feed items aredisplayed and a second user interface component 1220 in which publishedfeed items are displayed. The first user interface component may includeone or more types of feed items 1211, 1212, 1213 that the user mayselect to create a feed item 1214 of the selected type. Depending onwhich type of feed item is selected, the displayed feed item 1214 maycontain different fields and elements. Previously published feed items1222, 1224 may be displayed in the second user interface component 1220.An agent handling a customer call may use the features of the userinterface 1200 to perform tasks related to the issue associated with thecustomer call, such as composing an internal note with details about theissue, changing the status of a case from pending to resolved, orsending the customer an email with information related to the case.

In some implementations, the second user interface component 1220 maydisplay all of the feed items published in the currently open case.Alternatively, the second user interface component may display only themost recent updates to the currently open case

In FIG. 9, at block 908, the computing device performing method 900,responsive to a request to compose a second feed item, displays a secondprompt for second feed item data. In some implementations, the computingdevice displays the second prompt without publishing the first feeditem. The second prompt may be associated with a second action and bedisplayed in the first user interface component of the user interface.

In some implementations, an agent, having composed an email to thecustomer, may wish to also write an internal note, and he may wish topublish both items at the same time, rather than composing the email,publishing the email, then composing the note, and publishing the note.Being able to compose multiple feed items without having to publish onebefore moving on to another may save the agent valuable time and mouseclicks, and allow the agent to cross-verify information that he isentering in the various feed items before publishing all of the feeditems at the same time.

In some implementations, the request to compose a second feed item maybe triggered by clicking on one of the feed item types 1211, 1212, 1213of FIG. 12.

FIG. 13 shows an example of a graphical user interface (GUI) including apresentation of a user interface for publishing feed items, inaccordance with one or more implementations. FIG. 13 illustrates anexample of a Service Console page where an agent is presented with auser interface in which he may click on an internal note 1312 to composea new internal note without publishing any unpublished feed items 1314in the first user interface component 1310. Responsive to clicking onthe internal note button 1312, the computing device displaying the userinterface 1300 may display an internal note prompt 1315 for the agent toenter the text for the internal note, while the previously composedemail 1314 remains unpublished.

In FIG. 9, at block 912, the computing device performing method 900receives, at the second prompt, second feed item data for a second feeditem. The second feed item may be part of the same case that the firstfeed item is part of, and may be associated with the second action.

In some implementations, the first feed item may have a different feeditem type than the second feed item. For example, the first feed itemmay be an email to the customer and the second feed item may be aninternal note for the agent. In other implementations, the first andsecond feed items may have the same feed item type. For example, thefirst and second feed items may both be internal notes, or they may bothbe file attachments that the agent wishes to include in the case.

In some implementations, the first and second prompts may be displayedin the first user interface component, which contains unpublished feeditems. The agent may enter feed item data into both prompts withoutpublishing either of the feed items.

FIG. 14 shows an example of a graphical user interface (GUI) including apresentation of a user interface for publishing feed items, inaccordance with one or more implementations. FIG. 14 illustrates anexample of a Service Console page where an agent is presented with twoprompts 1414, 1415 in which the agent may enter feed item data beforepublishing them together.

In some implementations, the computing device performing method 900 may,responsive to an instruction to close the first or second prompt,display a warning that the respective feed item data has not yet beenpublished, as described at block 916 of FIG. 9. As an example, the agentmay, after opening the first and second prompt and composing the twofeed items, decide to not publish one of the feed items and elect toclose one of the prompts. When he selects a prompt to close, thecomputing device may display in the user interface a warning that theprompt has not been published and that the information in theunpublished feed item may be lost by closing the prompt. In some otherimplementations, optional block 916 is omitted from method 900.

In some implementations, the user may be presented with an option tosave the feed item that he has elected to close without publishing. Inthese implementations, the user may save a draft of the feed item forlater publishing.

FIG. 10 shows a flowchart of an example of a computer implemented method1000 for composing and batch publishing feed items in a user interfacein a feed-based interaction context, in accordance with someimplementations. FIG. 10 is described with references to the examples ofFIGS. 12-15.

In FIG. 10, at block 1002, a computing device provides a first promptfor display in a first user interface component of the user interface,the first prompt being associated with a first action, as generallydescribed above at block 902 of FIG. 9.

In FIG. 10, at block 1004, the computing device performing method 1000receives feed item data for a first feed item. The feed item data may bereceived at a prompt displayed in the first user interface component.The first user interface component may be configured to displayunpublished feed items. The user interface may include a second userinterface component that is configured to display published feed items,as generally described above at block 904 of method 900.

In FIG. 10, at block 1008, the computing device performing method 1000,responsive to a request to compose a second feed item, displays a secondprompt for second feed item data. In some implementations, the computingdevice displays the second prompt without publishing the first feeditem. The second prompt may be displayed in the first user interfacecomponent of the user interface, as generally described above at block908 of method 900.

In FIG. 10, at block 1012, the computing device performing method 1000receives, at the second prompt, second feed item data for a second feeditem. The second feed item may be part of the same case that the firstfeed item is part of, as generally described above at block 912 ofmethod 900.

In FIG. 10, at block 1020, the computing device performing method 1000displays a first indicator and a second indicator indicating that thefirst and second feed items have not been published. As an example, ifthe first feed item is an email to a customer and the second feed itemis an internal note, the first indicator may be an icon related to anemail, and the second indicator may be an icon related to an internalnote. In some implementations, there may be as many indicators as thereare unpublished feed items, with each indicator indicating the feed itemtype of a corresponding unpublished feed item.

In some implementations, the indicators may be displayed on the buttonfor publishing the unpublished feed items. In other implementations, theindicators may be displayed in the first user component. In yet otherimplementations, the indicators may be displayed elsewhere in the userinterface. For example, in FIG. 14, the indicators 1446 are displayed onthe Publish & Next button 1440, which indicates to the user that the twofeed items corresponding to the indicators have not yet been published.This way, a user can quickly determine which and how many feed items areunpublished in the first user interface component.

In some implementations, when an unpublished feed item is closed orsaved as a draft, the indicator corresponding to the closed feed itemmay disappear, indicating that the feed item will not be published whenthe agent clicks on one of the publish buttons 1442, 1440.

In FIG. 10, at block 1030, the computing device performing method 1000,responsive to an instruction to publish the first and second feed items,transmits the first feed item data and the second feed item data to aserver to be stored and published at substantially the same time.

In some implementations, the instruction to publish the first and secondfeed items may be received from a call agent submitting the request viathe user interface. In other implementations, the instruction may bereceived via an application programming interface (API) call. As anexample, a user maybe be using a mobile application to send API calls tothe application, and one of the API calls may be a request to publishthe first and second feed items.

In some implementations, the agent may trigger the instruction topublish the first and second feed items by clicking on a publish button.In FIG. 14, the agent may click on the “Publish only” button 1442, orthe “Publish & Next” button 1440, both of which will send theinstruction to the server to publish the first and second unpublishedfeed items 1414, 1415 displayed in the first user component 1410. Theinstruction to the server may be accompanied by the feed item dataentered in the first and second prompts for the server to store andpublish in the feed.

In some implementations, while the first and second feed items arepublished at substantially the same time, the first and second feed itemmay be published in the order of when the prompts were opened in theuser interface. In some implementations, the order of the unpublishedfeed items may be changed. This might be done by clicking and draggingone of the prompts up or down within the first user interface component.

In FIG. 10, at block 1032, the computing device performing method 1000displays a second case in the user interface. The second user interfacecomponent may display published feed items of the case. In someimplementations, the first user interface component does not display anyunpublished feed items of the case when the second case is firstdisplayed in the user interface.

In some implementations, when the agent opens two prompts and enters thefirst and second feed item data, the agent may select the “Publish &Next” button 1440 in FIG. 14 to publish the two feed items, and toinstruct the computing device to display the next case. In someimplementations, the agent may have a queue of cases that he is workingthrough to publish updates for, whether it is to send an email to acustomer or to change the status of a case. When the agent is done withcomposing the feed items that he wishes to publish for a case, and wantsto also move on to the next case, he can use the “Publish & Next” button1440 to publish the feed items and move on to the next case in one clickof the button. In some implementations, the queue of cases may beassigned to the agent by an administrator of the Service Console in aparticular order. The “Publish & Next” feature allows an agent to createany number of feed items for a case without publishing themindividually, publish them with one click, and automatically move on tothe next case in the agent's queue.

In FIG. 10, at block 1034, the computing device performing method 1000displays the published first and second feed items in the second userinterface component. As an example, an agent may wish to compose aninternal note and an email to a customer for a case, publish the noteand email, and then do some other work related to the same case. In thissituation, the user could click on the “Publish only” button 1442 ofFIG. 14 to publish the unpublished feed items and display the publishedfeed items in the second user interface component while leaving the caseopen in the user interface.

In some implementations, once the unpublished feed items are published,the first user interface component may become smaller in the userinterface and the second user interface component may expand in the userinterface to display the newly published feed items. The second userinterface component may also display previously published feed items aswell. In some implementations, the second user interface componentdisplays all feed items that have been published for the case. In otherimplementations, the second user interface component may display onlythe most recently published feed items of the case.

FIG. 15 shows an example of a graphical user interface (GUI) including apresentation of a user interface for publishing feed items, inaccordance with one or more implementations. FIG. 15 illustrates anexample of a Service Console page where an agent has composed andpublished a first and second feed item 1522, 1524. The second userinterface component 1520 displays both the first and second feed items1522, 1524, and two previously published feed items 1526, 1528 as well.The first user interface component 1510 has been collapsed in the userinterface because the agent does not have any unpublished feed itemsopen in first user interface component 1510. When presented with thisuser interface 1500, the user has the option to select a feed item type1511, 1512, 1513 to open up a prompt in the first user interfacecomponent 1510 to compose a new feed item. Alternatively, the user mayalso interact with other areas of the user interface 1500, such as thehighlights panel 1560 or the context pane 1570.

FIG. 11 shows a flowchart of an example of a computer implemented method1100 for composing and batch publishing feed items in a user interfacein a feed-based interaction context, in accordance with someimplementations. FIG. 11 is described with references to the examples ofFIGS. 12-15.

In FIG. 11, at block 1102, a computing device provides a first promptfor display in a first user interface component of the user interface,the first prompt being associated with a first action, as generallydescribed above at block 902 of FIG. 9.

In FIG. 11, at block 1104, the computing device performing 1100 receivesfeed item data for a first feed item. The feed item data may be receivedat a prompt displayed in the first user interface component. The firstuser interface component may be configured to display unpublished feeditems. The user interface may include a second user interface componentthat is configured to display published feed items, as generallydescribed above at block 904 of method 900.

In FIG. 11, at block 1108, the computing device performing method 1100,responsive to a request to compose a second feed item, displays a secondprompt for second feed item data. In some implementations, the computingdevice displays the second prompt without publishing the first feeditem. The second prompt may be displayed in the first user interfacecomponent of the user interface, as generally described above at block908 of method 900.

In FIG. 11, at block 1112, the computing device performing method 1100receives, at the second prompt, second feed item data for a second feeditem. The second feed item may be part of the same case that the firstfeed item is part of, as generally described above at block 912 ofmethod 900.

In FIG. 11, at block 1122, the computing device performing method 1100,responsive to a request to compose a third feed item, displays a thirdprompt for third feed item data. The third prompt is displayed in thefirst user interface component, which contains unpublished feed items.The third prompt is displayed without publishing the first and secondfeed items.

Similar to block 1108 of FIG. 11, the agent may compose two feed itemsand wish to compose a third feed item without publishing the first twofeed items. Returning to FIG. 14, the agent may do this by clicking onone of the feed item types 1411, 1412, 1413, which may cause a thirdprompt to be displayed in the first user interface component 1410. Thethree prompts may be displayed in the order in which they were opened,or in any other order of the agent's choosing.

In FIG. 11, at block 1124, the computing device performing method 1100receives, at the third prompt, third feed item data for a third feeditem. The third feed item is related to the same case as the first twofeed items displayed in the first user interface component. The user mayinput the third feed item data by typing it into a text box, selecting afile for attachment, selecting one or more options presented in theprompt, and the like.

In FIG. 11, at block 1130, the computing device performing method 1100,responsive to an instruction to publish the first, second, and thirdfeed items, transmits the first, second, and third feed item data to aserver to be stored and published at substantially the same time, asgenerally described above at block 1030 of method 1000.

In FIG. 11, at block 1132, the computing device performing method 1100displays a second case in the user interface. The second user interfacecomponent displays the published feed items of the second case, asgenerally described above at block 1032 of method 1000.

In FIG. 11, at block 1134, the computing device performing method 1100displays the published first, second, and third feed items in the seconduser interface component, as generally described above at block 1032 ofmethod 1000.

These and other aspects of the disclosure may be implemented by varioustypes of hardware, software, firmware, etc. For example, some featuresof the disclosure may be implemented, at least in part, bymachine-readable media that include program instructions, stateinformation, etc., for performing various operations described herein.Examples of program instructions include both machine code, such asproduced by a compiler, and files containing higher-level code that maybe executed by the computer using an interpreter. Examples ofmachine-readable media include, but are not limited to, magnetic mediasuch as hard disks, floppy disks, and magnetic tape; optical media suchas CD-ROM disks; magneto-optical media; and hardware devices that arespecially configured to store and perform program instructions, such asread-only memory devices (“ROM”) and random access memory (“RAM”).

While one or more implementations and techniques are described withreference to an implementation in which a service cloud console isimplemented in a system having an application server providing a frontend for an on-demand database service capable of supporting multipletenants, the one or more implementations and techniques are not limitedto multi-tenant databases nor deployment on application servers.Implementations may be practiced using other database architectures,i.e., ORACLE®, DB2® by IBM and the like without departing from the scopeof the implementations claimed.

Any of the above implementations may be used alone or together with oneanother in any combination. Although various implementations may havebeen motivated by various deficiencies with the prior art, which may bediscussed or alluded to in one or more places in the specification, theimplementations do not necessarily address any of these deficiencies. Inother words, different implementations may address differentdeficiencies that may be discussed in the specification. Someimplementations may only partially address some deficiencies or just onedeficiency that may be discussed in the specification, and someimplementations may not address any of these deficiencies.

While various implementations have been described herein, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of the present applicationshould not be limited by any of the implementations described herein,but should be defined only in accordance with the following andlater-submitted claims and their equivalents.

What is claimed is:
 1. A computer-implemented method for composing andbatch publishing feed items in a user interface of an online socialnetwork, the method comprising: causing display of the user interface ona display device, the user interface comprising a first user interfacecomponent and a second user interface component in the same window, thefirst user interface component comprising a plurality of unpublishedfeed items, the second user interface component comprising a pluralityof previously published feed items from a social media feed of theonline social network, the social media feed associated with a firstrecord stored in a database; receiving, via a first prompt in the firstuser interface component, first feed item data for a first feed itemrelated to the first record; receiving a request to compose a secondfeed item; receiving, via a second prompt in the first user interfacecomponent, second feed item data for a second feed item related to thefirst record, the first feed item remaining unpublished while the secondfeed item data is received; receiving a single input requestingsimultaneous publishing of at least the first feed item and the secondfeed item; and responsive to receiving the single input, causing thesecond user interface component to be updated to simultaneously includeat least the first feed item and the second feed item among theplurality of previously published feed items from the social media feedof the online social network.
 2. The method of claim 1, furthercomprising: responsive to receiving the single input, transmitting thefirst feed item data and the second feed item data to the database to bestored.
 3. The method of claim 2, wherein the single input requestingsimultaneous publishing of at least the first feed item and the secondfeed item is received from the user interface.
 4. The method of claim 2,wherein the single input requesting simultaneous publishing of at leastthe first feed item and the second feed is received via an ApplicationProgramming Interface (API) call.
 5. The method of claim 2, furthercomprising: causing display of a second record in the user interface,the second user interface component displaying published feed items ofthe second record.
 6. The method of claim 1, further comprising:receiving a request to compose a third feed item of the unpublished feeditems receiving, via a third prompt in the first user interfacecomponent, third feed item data for a third feed item related to thefirst record, the first feed item and the second feed item remainingunpublished while the third feed item data is received; receiving thesingle input includes requesting simultaneous publishing of at least thefirst feed item, the second feed item, and the third feed item; andresponsive to receiving the single input, causing the second userinterface component to be updated to simultaneously include at least thefirst feed item, the second feed item, and the third feed item among theplurality of previously published feed items from the social media feedof the online social network.
 7. The method of claim 6, furthercomprising: causing display of a second record in the user interface,the second user interface component displaying published feed items ofthe second record.
 8. The method of claim 6, further comprising: causingdisplay of a first, second, and third indicator indicating that thefirst, second, and third feed items have not been published.
 9. Themethod of claim 1, further comprising: causing display of a firstindicator and a second indicator indicating that the first and secondfeed items have not been published.
 10. The method of claim 1, whereinthe first and second feed items have a feed item type, the feed itemtype being one of: an email, a note, a flag, a status change, anattachment, a comment, a social media message, and a calendar item. 11.The method of claim 1, further comprising: receiving an instruction toclose the first or second prompt, and responsive to the instruction toclose the first or second prompt, causing the display of a warning thatthe respective feed item data has not yet been published.
 12. One ormore computing devices for composing and batch publishing feed items ina user interface in a feed-based interaction context, the one or morecomputing devices comprising: one or more processors operable to executeone or more instructions to: cause display of the user interface on adisplay device, the user interface comprising a first user interfacecomponent and a second user interface component in the same window, thefirst user interface component comprising a plurality of unpublishedfeed items, the second user interface component comprising a pluralityof previously published feed items from a social media feed of theonline social network, the social media feed associated with a firstrecord stored in a database; receive, via a first prompt in the firstuser interface component, first feed item data for a first feed itemrelated to the first record; receive a request to compose a second feeditem; receive, via a second prompt in the first user interfacecomponent, second feed item data for a second feed item related to thefirst record, the first feed item remaining unpublished while the secondfeed item data is received; receive a single input requestingsimultaneous publishing of at least the first feed item and the secondfeed item; and responsive to receiving the single input, cause thesecond user interface component to be updated to simultaneously includeat least the first feed item and the second feed item among theplurality of previously published feed items from the social media feedof the online social network.
 13. The one or more computing devices ofclaim 12, the one or more processors further operable to execute one ormore instructions to: responsive to the single input, transmit the firstfeed item data and the second feed item data to the database to bestored.
 14. The one or more computing devices of claim 13, the one ormore processors further operable to execute one or more instructions to:cause display of a second record in the user interface, the second userinterface component displaying published feed items of the secondrecord.
 15. A non-transitory computer-readable storage medium storinginstructions executable by one or more processors to cause a method tobe performed for composing and batch publishing feed items in a userinterface in a feed-based interaction context, the method comprising:causing display of the user interface on a display device, the userinterface comprising a first user interface component and a second userinterface component in the same window, the first user interfacecomponent comprising a plurality of unpublished feed items, the seconduser interface component comprising a plurality of previously publishedfeed items from a social media feed of the online social network, thesocial media feed associated with a first record stored in a database;receiving, via a first prompt in the first user interface component,first feed item data for a first feed item related to the first record;receiving a request to compose a second feed item; receiving, via asecond prompt in the first user interface component, second feed itemdata for a second feed item related to the first record, the first feeditem remaining unpublished while the second feed item data is received;receiving a single input requesting simultaneous publishing of at leastthe first feed item and the second feed item; and responsive toreceiving the single input, causing the second user interface componentto be updated to simultaneously include at least the first feed item andthe second feed item among the plurality of previously published feeditems from the social media feed of the online social network.
 16. Thenon-transitory computer-readable storage medium of claim 15, the methodfurther comprising: responsive to receiving the single input,transmitting the first feed item data and the second feed item data tothe database to be stored.
 17. The non-transitory computer-readablestorage medium of claim 16, the method further comprising: causingdisplay of a second record in the user interface, the second userinterface component displaying published feed items of the secondrecord.